Originally by: brinelan

---

Edited by: brinelan on 24/04/2007 20:39:08
With things being recoded to move more processing to the GPU, will SLI support be considered or included?

---

Originally by: Nisse Owned

---

Though, is DX10 cards even out yet... I know HL2 and most source engine based games is possible to force an old card to support a higher hardware level at the cost of performance. Would be cool if it would be possible to do like that with eve aswell(Poor me can't upgrade graphics card in my laptop )

---

Originally by: Scetrov

---

It is good to see that rolling updates are on the agenda, I would be really interested to know how many EVE players have which graphics cards, I don't suppose CCP have that data to hand without players submitting that information themselves... torn between privacy and data mining being cool!.

Also for some reason, I feel the need to post this again...

---

Originally by: Nifel

---

Will the new EVE client (or the current EVE client even) use RAM for cached items instead of the hd? Preferrably shared between multiple clients >_>.

---

Originally by: Broska

---

Will the new engine make fleet battles without the server crashing / half the participants crashing, a possibility again?

---

Originally by: Solbright

---

1 - Trinity 2 for DX9
2 - Trinity 2 for DX10

---

Originally by: LancerSix

---

Edited by: LancerSix on 24/04/2007 22:23:51
How does Ambulation factor into this? Do you think we may see at least some elements of it surface with the new engine at the end of the year?

I seriously can't wait .

/me sells his soul for beta .

---

Originally by: Matthew

---

Originally by: Solbright

---

Slipstream network layer
Some DRM thingy or, if lucky, an attempt to opensource the client. Release date: 2009/2010.

---

Don't think this will be to do with DRM or opensource at all. All it really sounds like is is a new pile of code for handling client-server communications. The current code seems to be good at sending lots of little messages, but not so good when you've got really big messages to go across the link (e.g. the market listing for shuttles). Hopefully slipstream will fix those issues and give a generally more robust connection to the server for less random disconnects.

---

Originally by: Dr Aryandi

---

Originally by: Nate D

---

Originally by: "CCP Oveur"

---

*snip*
...we're always moving mature code from Python to C if it's highly utilized.

*snip*
We regularily refactor code, optimize, move to C or simply replace code regularly.

---

Pardon my inadequate knowledge of coding but what I take from these statements is that C code is faster and better than Python code. If this is the case, why isn't the code written in C to begin with?

Not a complaint, just a question.
-Nate

---

C code executes faster. I.e. if you want to add 1000 numbers to 1000 other numbers then C will probably do it faster.

Python though is much faster and easier to write/tweak/change/test etc.

So development can be done much faster in python, then performance critical sections of code get refactored in C (you can call between C and python inside one program).

C vs Python is a trade-off between raw performance and development timescales.

---